View integration of behavior in object-oriented databases

ion request ROOM-RES requested ROOM-RES confirmed r r confirm ROOM-RES used r use r r (c) abstracted view ROOM-RES Figure 14: Integration steps for view ROOM-RES Example: During abstraction, labels rr and rs of ROOM-RES, which correspond to label r in CAR-RES by inclusion, are abstracted to label r; the di erent re nements of the abstract activity use, which correspond to each other by a subnet correspondence, are abstracted to a single activity use, yielding the abstracted sub-views shown in part (c) of the gures. 3. Integration and composition: The abstract sub-views are integrated to the integrated object life-cycle B: (a) Integration: Naming con icts are resolved by de ning an object life-cycle Bi for each  Bi, where the former is isomorphic to the latter. The only di erence between Bi and  Bi is that each activity, state, and label of  Bi gets a new identity in Bi (and, possibly, a new name). Correspondences between  B1 and  B2 are considered in that corresponding elements get the same identity and di erent 23 request CAR-RES requested CAR-RES confirmed i, r r i, r confirm r CAR-RES toInsure CAR-RES insured i i CAR-RES driving depart r return r CAR-RES used r